Skip to content

Release Review: ClickToDial r1.2 (rc Spring26)#83

Merged
YadingFang merged 3 commits intorelease-snapshot/r1.2-1ee4853from
release-review/r1.2-1ee4853
Mar 9, 2026
Merged

Release Review: ClickToDial r1.2 (rc Spring26)#83
YadingFang merged 3 commits intorelease-snapshot/r1.2-1ee4853from
release-review/r1.2-1ee4853

Conversation

@camara-release-automation
Copy link
Copy Markdown
Contributor

@camara-release-automation camara-release-automation bot commented Mar 9, 2026

Release r1.2 (rc)

Codeowners update and review this PR. After codeowner and release management approval, merge into the release snapshot to create a draft release.

APIs in this release

API Version Status
click-to-dial 0.1.0-rc.1 rc

Dependencies: Commonalities r4.1, ICM r4.1

Codeowner Review

Update this PR:

  • All relevant changes copied into Added / Changed / Fixed / Removed (per API as needed)

Confirm readiness:

  • API version numbers match the intent declared in release-plan.yaml
  • API definitions comply with declared Commonalities version
  • API documentation is complete
  • Basic test cases are present (sunny day + main error cases)

Release Management Review

  • CHANGELOG follows the release documentation rules
  • Breaking changes are documented and version updates follow SemVer rules
  • All mandatory release assets for the APIs are present per the API status and confirmed
Required release assets per API status
Nr Asset alpha rc initial
public
stable
public
1 Release Plan M M M M
2 API Definition(s) M M M M
3 Commonalities compliance O M M M
4 API Documentation M M M M
5 User Stories O O O M
6 Test Cases (basic) O M M M
7 Test Cases (enhanced) O O O M
8 API Description O O M M

M = Mandatory, O = Optional — Full documentation

Verify snapshot content (during automation introduction phase only):

  • release-metadata.yaml content is correct
  • API version numbers and applicable extensions were generated correctly (server URLs, references, version fields)
  • README update looks correct (release tag, versions, latest vs pre-release)

Valid actions

  • Merge this PR when both codeowner and release management approvals are given — creates a draft release
  • /discard-snapshot in the Release Issue to discard, return to planned, and update content on main

Snapshot: r1.2-1ee4853

Updated changelog for release r1.2, adding new API features and correcting previous entries.
Copy link
Copy Markdown
Contributor

@YadingFang YadingFang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Checklist confirmed:

  • All relevant changes copied into Added / Changed / Fixed / Removed
  • API version numbers match release-plan.yaml
  • API definitions comply with Commonalities r4.1
  • API documentation is complete
  • Basic test cases are present

Copy link
Copy Markdown

@tanjadegroot tanjadegroot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OBSOLETE COMMENT - PLEASE IGNORE

The release should be r2.1 (not r1.2) as related to a different version of commonalities and ICM then r1.1

next steps:

  • in the Release Issue #82 type the command: /discard-snapshot wrong target release number
  • update the release-plan.yaml on main to target r2.1
  • the merge creates a new release issue for r2.1
  • in the new issue type : /create-snapshot

@hdamker: please confirm the above steps are OK

@tanjadegroot
Copy link
Copy Markdown

@hdamker convinced me that, while still doing prereleases it is OK to stay with the same rX number.
You can ignore my above comment I will go ahead and approve the PR

@tanjadegroot
Copy link
Copy Markdown

tanjadegroot commented Mar 9, 2026

/LGTM from Release Management

@YadingFang YadingFang merged commit 7a215bb into release-snapshot/r1.2-1ee4853 Mar 9, 2026
1 check passed
@YadingFang
Copy link
Copy Markdown
Contributor

@tanjadegroot Thank you very much for the review and approval! Really appreciate the guidance from you and @hdamker as we transition to this new automated process. I'll merge this PR now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants